"Implement Lockable and Confirmable Features in Devise Authentication" #133
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
"This pull request introduces the Lockable and Confirmable features for user authentication using Devise.
Changes Included:
Lockable:
Configured Devise to lock user accounts after 5 consecutive failed login attempts.
Added necessary database migrations to support failed_attempts and locked_at fields in the users table.
Confirmable:
Integrated email confirmation for new user registrations.
Added required fields (confirmation_token, confirmed_at, etc.) to the users table through migrations.
Initial Setup:
Adjusted Devise settings in the User model to enable both features.
Verified basic locking and confirmation mechanisms.
Pending Work:
Flash messages for account lock and confirmation status are not yet configured and will be addressed in a separate commit.
This update is part of improving user authentication security for the platform. Please review and share feedback before merging."